Version Packages (rc)#5413
Closed
ohalushchak-exadel wants to merge 1 commit into
Closed
Conversation
Bumps the prerelease package from 3.1.0-rc.10 to 3.1.0-rc.11 and updates the schema registry version metadata. Adds the generated 3.1.0-rc.11 schema, compliance, and protocol tarball artifacts, including the checksum sidecar. The cosign .sig/.crt sidecars are produced by the release workflow on merge. Rolls up the changesets merged since rc.10 — notably the required `seller_agent_url` on `context_match_request` (and the matching `identity_match_request` changeset). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![aao-release-bot[bot]](https://avatars.githubusercontent.com/u/221690821?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Mechanical rc.11 release rollup, internally consistent. Right shape for a Version Packages PR: source bump + generated dist artifacts, nothing hand-edited that the generator owns.
Things I checked
- Version strings agree across every surface, all rc.11:
package.json:3, bothpackage-lock.jsonroot +packages.""entries,static/schemas/source/index.json(adcp_versionandpublished_version), the newCHANGELOG.md## 3.1.0-rc.11section, and all 1037 added dist paths. Zero stale rc.10 paths introduced. Remaining lockfile churn is npmpeer: truemetadata only. .changeset/pre.jsonconsumes exactly one new entry —tmp-context-match-seller-agent-url— matching the single rc.11 CHANGELOG Minor entry.tmp-identity-match-seller-agent-urlwas already consumed and correctly not re-listed, consistent with the PR body noting it landed earlier.- CHANGELOG provenance: commit
563eaf4resolves to "spec(tmp): add required seller_agent_url to context_match_request (#5410)." - The only
static/schemas/source/**touch is the two version strings inindex.json— no field, type, enum, or required-list change. No wire-shape drift in this PR; the substantiveseller_agent_urlchange was reviewed and merged upstream in #5410. - Generated
dist/schemas/3.1.0-rc.11/tmp/context-match-request.jsoncarriesseller_agent_urlinrequiredwith the full description on the wire. The rollup actually emitted the rolled-up change. ad-tech-protocol-expert: sound. Minor categorization is correct, not spec drift —docs/reference/experimental-status.mdx:36states verbatim that onx-status: experimentalsurfaces "Required fields may become optional and vice versa," and the 3.x optional→required deprecation gate (versioning.mdx:176) binds stable surfaces only.context_match_requestis experimental at HEAD, so a new required field within a 3.x release is Minor, not Major.
Follow-ups (non-blocking — file as issues)
- The experimental-status policy attaches a 6-week breaking-change notice obligation (
experimental-status.mdx:43) totmpsurfaces. That obligation lived with #5410, not this PR — but worth confirming the notice was logged. Does not affect the semver tier or this tag.
One dry note: the release automation skipped this because has_release_artifacts matched the rc.10 dist already sitting in main's tree while package.json stayed rc.10. Cutting it by hand is fine; the gate keying off committed artifacts instead of the declared version is the thing worth a follow-up.
Ship it once CI validates the schema-release suite.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the prerelease package from
3.1.0-rc.10to3.1.0-rc.11and updates the schema registry version metadata.Adds the generated
3.1.0-rc.11schema, compliance, and protocol tarball artifacts, including the checksum sidecar. The cosign.sig/.crtsidecars are produced by the release workflow on merge (Sigstore OIDC bound to the workflow identity).Rolls up the changesets merged since rc.10 — notably the required
seller_agent_urloncontext_match_request(#5410), plus the matchingidentity_match_requestfield changeset and the other pending entries onmain.Why this was cut by hand
The release automation did not open this PR after #5410 merged: the
Releaseworkflow'shas_release_artifactscheck matched the already-committed rc.10 dist artifacts inmain's tree (package.jsonis still3.1.0-rc.10), so the changesets version-PR step was skipped and the run took the publish path instead. Same manual procedure as rc.10 (#5405):npm run version→ commit → "Version Packages (rc)" PR → merge publishes.Validation
npm run versionsucceeded (rc.11 schema/compliance/protocol artifacts generated). Schema-release tests pass locally:test:schemas(16),test:examples(42 — the now-requiredseller_agent_urlis present in both context-match fixtures),test:json-schema(282),test:composed(107),test:dist-schema-version-ids. Full CI runs here.Merging this tags + publishes
v3.1.0-rc.11.